Configuring Service.props
About Configuring Service.props
The service.props file is used to configure adapter behavior. service.props is located in the \config directory located under the Adapter’s GUID directory. You can create the directory and file if it does not yet exist. Properties that can be specified in service.props control things like logging and connection configuration. Many of the properties are specific to certain adapters; others are common across all adapters.
Service.props Properties
Property |
Applicable Adapter(s) |
Default and What It Controls |
|
---|---|---|---|
BYPASS_SEC_VALIDATION |
Oracle Apps |
N |
If set to Y, the secondary user validation is bypassed. If not, secondary user validation is performed. |
CLASSPATH |
All |
<none> |
(Optional) – The path to the JDBC driver. If the default CLASSPATH used when the Adapter process is started does not include an appropriate JDBC driver jar required to connect to the PowerCenter Repository Database, you will need to specify this service.props configuration |
CONN_SYNC |
Informatica, Oracle Apps, SAP |
N |
Setting this flag to Y allows synchronous connections without overloading the RDOnly Thread. If set to N, the adapter might stop trying to reconnect after an outage or downtime. |
DISCONN_ON_LOSTCONN |
Informatica |
N |
Setting this flag to Y avoids an unnecessary logout call to the Informatica server when the connection is lost. This logout call usually hangs. |
EnableDynamicPollingInterval |
All |
N |
Use to avoid frequent polling on long-running jobs. When set to Y in service.props of a particular adapter, these properties are enabled: |
HADOOP_JAVA_HOME |
Sqoop |
<none> |
Make sure that the Hadoop environment contains the Java version the TA Master is running on. |
IGNORE_CODES |
Informatica |
<none> |
This parameter can be set in service.props, job configuration and connection configuration parameters. The order of precedence is service.props (applicable for all jobs running in all connections), job level (only for that particular job), and connection (applicable for all jobs in the connection). This parameter is used to specify Informatica-specific error codes, separated by commas (,), that you want to ignore while running a job. |
IGNORESUBREQ |
Oracle Apps |
N |
Y or N. Setting this flag to Y stops huge job xml file transfers back and forth between the adapter and the AdapterHost during polls when a single request set has multiple sub-requests of more than 100. The default value is N or empty. |
kerbkdc |
MapReduce |
<none> |
If the Hadoop cluster is Kerberos secured, use this value to specify the KDC Server. For example, kerbkdc=172.25.6.112 |
kerbrealm |
MapReduce |
<none> |
If the Hadoop cluster is Kerberos secured, use this value to specify the Kerberos Realm. For example, kerbrealm=TIDALSOFT.LOCAL |
Keystore |
BusinessObjects, BusinessObjects BI, BusinessObjects DS, Cognos, JD Edwards, Oracle Applications, UCS Manager, VMware, Web Service |
<none> |
Specify Keystore=c:\\<adapter_certificate_directory>\\<your_trusted_keystore>.keystore when importing certificates into a Java keystore. |
LAUNCH_DELAY (in milliseconds) |
Informatica |
<none> |
This parameter can be set in service.props, job configuration and connection configuration parameters. The order of precedence is service.props (applicable for all jobs running in all connections), job level (only for that particular job), and connection (applicable for all jobs in the connection). If a non-zero value is set for this parameter, then the jobs are delayed for the specified number of milliseconds before being submitted to Informatica. |
LoginConfig |
BusinessObjects BI Platform, BusinessObjects Data Services |
<none> |
Specifies the location of the login configuration if using WinAD or LDAP authentication. For example: LoginConfig=c:\\windows\\bscLogin.conf where “c:\\windows\\bscLogin.conf” is the location of the login configuration information. Note the use of \\ if this is a Windows location. |
MaxLogFiles |
Informatica, JDBC, PeopleSoft |
50 |
(Optional) – Number of logs to retain. |
OUTPUT_ASYNC_LOGOUT |
Informatica |
N |
Setting this flag to Y avoids jobs getting stuck in Gathering Output status. |
OUTPUT_SYNC |
All |
Y |
Enables concurrent output gathering on a connection. To enable this feature, set the value to N. |
POLL_SYNC |
All |
Y |
Enables concurrent polling on connections of the same type. This is helpful when there is a heavily load on one connection of an adapter. The heavily loaded connection will not affect the other adapter connection. To enable this feature, set the value to N. |
QUERY_TIMEOUT |
Oracle Apps |
N |
Y or N. If set to Y, the timeout value defined using the parameter QUERY_TIMEOUT_VALUE is applied to the SQL queries. Default value is N or empty. |
QUERY_TIMEOUT_VALUE |
Oracle Apps |
unset |
The time period in seconds that SQL queries wait before timeout. If 0 or not set, there is no timeout. |
READPCHAINLOG |
SAP |
Y |
Used to control the log gathering in SAP Process Chain jobs. This property depends on the Summary Only checkbox of the job definition Options tab. |
SCANFOR_SESSIONSTATS |
Informatica |
Y |
Y or N – Set this parameter to N to turn off the default behavior of Informatica jobs collecting the session statistics during the job run. |
SCANFOR_SESSIONSTATS_AFTER_WF_ENDS |
Informatica |
N |
Y or N – Set this parameter to Y to turn off the gathering of session statistics during each poll for the status of Informatica jobs. |
TDLINFA_LOCALE |
Informatica |
<none> |
Points to the Load Manager Library locale directory. See “Configuring the Informatica Adapter” in the Informatica Adapter Guide for how to set this for Windows and Unix environments. |
TDLINFA_REQUESTTIMEOUT |
Informatica |
<none> |
(Optional) – The number of seconds before an API request times out. The default is 120 seconds, if not specified. |
TDLJDBC_LIBPATH |
JDBC |
<none> |
(Windows only, optional) An alternate path to the JDBC library files. The library file path should have been configured given system environment variables. This option is available in case you wish to use an alternate set of libraries and may be helpful for trouble-shooting purposes. |
TDLJDBC_LOCALE |
JDBC |
<none> |
The path to the JDBC locale files. |
TRANSACTION_LOG_BATCH_SIZE |
MS SQL |
5000 |
Set this parameter if more than 5000 lines need to be read from the transaction table. |
version_pre898 |
JD Edwards |
N |
If running on a JD Edwards server version that is less than 8.9.8, set version_pre898=Y. |